Ignore inline keys when they appear in an inline codeblock. - #2542

Before even considering to merge this, please clean up your code and remove unwanted console.log() statements.

Woops, sorry about that. console.log have been removed.

@holroy This PR should now be more comprehensive than the initial proposal.
Please let me know what you think about it and if I missed anything. I’m happy to learn!

After looking a little closer into the actual change, I think we need to discuss this a little further. Your code ignores any escaped backticks, and it is used in a context where the function is indicating that we're only looking for the inline separator.

This means that this function is most likely also used when we're looking for separators in entire paragraphs being used as field definitions, and possibly other cases.

In other words, the scoping of this change is wrong, although the idea of ignoring inline keys could be pursued further. Where and how to it though needs to be discussed a little further.

Hehe, that’s the kind of thing I expected to have missed.

I’m happy to relocate it to where it belong. Would you be able to advise on the proper location?

With regards to the backtick escaping, I tried to replicate what obsidian does in the markdown interpretation, i.e. escape backticks only outside codeblocks. So here we only ignore the backtick if it is found to be an "entry" to a code block.
I didn’t add specific tests for triple ` blocks. As far as I can see it is not causing issues in the code rendering.
I don’t use inline fields (yet) so I don’t know if I broke anything on that side either (hopefully not).

I'm currently working on releasing a new version of dataview and having some issues with that, but in due time I'll come back to you hopefully. Not sure where and how to tackle this issue, but using findSeparator() just seems wrong.